Summary

Five open PRs change docs/branch-review-ledger.md and nothing else, contributing fifteen review records between them. This lands all fifteen in one commit so the five originals can be closed rather than each carrying its own main sync and CI cycle. A sixteenth record covers the #1192 landing, added here rather than as a seventh ledger PR.

The queue cost of these five is out of proportion to sixteen lines of documentation. Each needs a main sync to become mergeable, and each sync risks the union merge driver re-appending records both sides already carry — which is exactly what blocked #1192's check:branch-review-ledger twice in one hour today, and what outstanding item #82 tracks. Batching removes five sync-and-rerun loops.

Rows from the five source PRs are copied verbatim from each PR head, then asserted byte-identical against their source after appending, so nothing is paraphrased, reordered within a PR, or lost. No existing record is edited or removed; this is a pure 16-line append.

The five source PRs are left open. Closing them is the author's call, and they can be closed as landed here once this merges.

Verification

Documentation-only change to a single file, so the source-code gates in the template do not apply. What was run:

• npm run check:branch-review-ledger — 957 records, union merge active, no conflict markers, no exact duplicates
• npm run docs:check-links — 1192 repo path references resolve
• prettier --check docs/branch-review-ledger.md — clean
• git diff origin/main...HEAD --numstat reports 16 insertions and 0 deletions, so no existing record or line ending was disturbed
• Byte-identity assertion: all 15 carried-over rows match their source PR head exactly
• Verification not run: npm run verify:pr-local and npm run verify:ui. This change cannot affect application behavior — it adds table rows to one markdown file and touches no source, test, config, or build input.

Risk and rollout

• Risk: low — additive documentation only, with no code, schema, or configuration effect
• Rollback: revert the single squash commit; the source PRs remain open and can still be merged individually
• Provider or production effects: None

Clinical Governance Preflight

Not applicable. This change touches no ingestion, answer generation, search/ranking, source rendering, document access, privacy, production environment, or clinical output surface. The Supabase target is unchanged at Clinical KB Database (sjrfecxgysukkwxsowpy).

Notes

• Every row was checked against current main first; none had already landed by another route.
• Ordering appends by source PR (docs: ledger closeout for merged PR #1162 #1206, docs(ledger): record Cursor Bugbot review of PR #1186 #1207, docs: record PR #1090 prlanded outcome in branch review ledger #1210, docs: ledger PR #1197 Bugbot do-not-merge review #1211, docs: ledger prlanded merge for PR #1197 #1224) and preserving each PR's internal order keeps the records readable against the originals.